Traffic list generation for passenger conveyance

ABSTRACT

A passenger tracking system includes a multiple of sensors for capturing depth map data of objects. A processing module in communication with the multiple of sensors to receive the depth map data, the processing module uses the depth map data to track an object and calculate passenger data associated with the tracked object to generate a passenger tracking list that tracks each individual passenger in the passenger data from an origin lobby to a destination lobby and through an in-car track between the origin lobby and the destination lobby.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/089,625, filed Apr. 4, 2016, which claims priority of CN 201510158110.5, filed Apr. 3, 2015.

BACKGROUND

The present disclosure relates to a passenger conveyance and, more particularly, to a depth sensor based control for an elevator.

Elevator performance can be derived from a number of factors. To an elevator passenger, an important factor can include travel time. For example, as time-based parameters are minimized, passenger satisfaction with the service of the elevator can improve. Modern elevator systems may still provide opportunities for improved passenger experience and traffic performance.

Typically, in a building with many people inside, efficient elevator usage may be complicated since certain time periods may by high traffic times, while others will be low traffic which may create inconvenience and delay for users, both those in the car and those waiting for a car.

Modern elevator systems may still provide opportunities for improved passenger experience and traffic performance.

SUMMARY

A passenger tracking system according to one disclosed non-limiting embodiment of the present disclosure can include one or more sensors for capturing sensor data; and a processing module in communication with the one or more sensors to receive the sensor data, where the processing module uses the sensor data to track an object and calculate passenger data associated with the tracked object to generate a passenger tracking list that tracks a passenger in the sensor data from an origin conveyance lobby to a destination conveyance lobby.

A further embodiment of the present disclosure may include, wherein at least one of the one or more sensors for capturing sensor data is located in a conveyance lobby adjacent to a conveyance system.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein at least one of the one or more sensors for capturing sensor data is located in a conveyance passenger enclosure.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein the sensor data is at least one of 2D and 3D depth data from a depth-sensing sensor.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein the depth-sensing sensor comprises a structured light measurement, phase shift measurement, time of flight measurement, stereo triangulation device, sheet of light triangulation device, light field cameras, coded aperture cameras, computational imaging techniques, simultaneous localization and mapping (SLAM), imaging radar, imaging sonar, scanning LIDAR, flash LIDAR, Passive Infrared (PIR) sensor, and small Focal Plane Array (FPA), or a combination comprising at least one of the foregoing.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein the processing module calculates an object parameter of the tracked object, wherein the object parameter comprises an object count, a location, a size, a direction, an acceleration, a velocity, an object classification, or a combination comprising at least one of the foregoing.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein the processing module calculates the passenger data if the tracked object is classified as a passenger.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein a passenger is tracked in at least one of an origin conveyance lobby, a conveyance passenger enclosure, a destination conveyance lobby.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein a passenger is tracked by two trackers when within the respective lobby.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein the two trackers include a head-shoulder tracker and a body tracker.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein the head-shoulder tracker is based on online boosting and the body tracker is based on particle filtering.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein a unique passenger identity is maintained during a passenger transition from at least one of an origin conveyance lobby to a conveyance passenger enclosure and a conveyance passenger enclosure to a destination conveyance lobby.

A method of passenger tracking for a passenger conveyance system, the method according to another disclosed non-limiting embodiment of the present disclosure can include tracking an individual passenger in an origin conveyance lobby; tracking the individual passenger while within a conveyance passenger enclosure from the origin conveyance lobby; and tracking the individual passenger from the conveyance passenger enclosure into a destination conveyance lobby to generate a traffic list.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein the tracking is performed using sensor data from a sensor in the conveyance passenger enclosure.

A further embodiment of any of the foregoing embodiments of the present disclosure may include tracking the individual passenger while in the conveyance passenger enclosure.

A further embodiment of any of the foregoing embodiments of the present disclosure may include tracking the head of each individual passenger.

A further embodiment of any of the foregoing embodiments of the present disclosure may include detection the head of each individual passenger via a circle-Hough transform and tracking the head via particle filtering.

A further embodiment of any of the foregoing embodiments of the present disclosure may include adjusting the head detection result to enclose each individual passenger based on optical flow.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein at least one of tracking the individual passenger while within a conveyance passenger enclosure from the origin conveyance lobby and tracking the individual passenger from the conveyance passenger enclosure into a destination conveyance lobby comprises a tracking hand over approach.

A further embodiment of any of the foregoing embodiments of the present disclosure may include edge weighting a graph-based optimization.

A further embodiment of any of the foregoing embodiments of the present disclosure may include edge weighting by order and time difference.

A further embodiment of any of the foregoing embodiments of the present disclosure may include, wherein at least one of tracking the individual passenger while within a conveyance passenger enclosure from the origin conveyance lobby and tracking the individual passenger from the conveyance passenger enclosure into a destination conveyance lobby to generate a traffic list comprises conveyance passenger enclosure door open/close identification.

A further embodiment of any of the foregoing embodiments of the present disclosure may include combining a multiple of traffic lists for each individual passenger over time.

A further embodiment of any of the foregoing embodiments of the present disclosure may include combining a multiple of traffic lists for each of a multiple of individual passenger over time with time as a parameter to facilitate statistical distribution determination of usage for an entire building.

A further embodiment of any of the foregoing embodiments of the present disclosure may include combining a multiple of traffic lists for each of a multiple of individual passenger over time with time as a parameter to facilitate statistical distribution determination of usage for a geographic area.

A further embodiment of any of the foregoing embodiments of the present disclosure may include combining a multiple of traffic lists for each of a multiple of individual passengers over time with time as a parameter to facilitate statistical distribution determination of usage for daily load estimation.

A further embodiment of any of the foregoing embodiments of the present disclosure may include combining a multiple of traffic lists for each of a multiple of individual passenger over time with time as a parameter to facilitate statistical distribution determination of usage for system diagnostics.

The foregoing features and elements may be combined in various combinations without exclusivity, unless expressly indicated otherwise. These features and elements as well as the operation thereof will become more apparent in light of the following description and the accompanying drawings. It should be appreciated, however, the following description and drawings are intended to be exemplary in nature and non-limiting.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features will become apparent to those skilled in the art from the following detailed description of the disclosed non-limiting embodiment. The drawings that accompany the detailed description can be briefly described as follows:

FIG. 1 is a schematic view of an elevator system according to one disclosed non-limiting embodiment;

FIG. 2 is a block diagram of an elevator system according to another disclosed non-limiting embodiment;

FIG. 3 is a perspective view of an elevator system according to another disclosed non-limiting embodiment;

FIG. 4 is a block diagram of an algorithm for an elevator system according to another disclosed non-limiting embodiment;

FIG. 5 is a block diagram of an algorithm for an elevator system according to another disclosed non-limiting embodiment;

FIG. 6 is a block diagram for an elevator system according to another disclosed non-limiting embodiment;

FIG. 7 is a block diagram of an algorithm for an elevator system according to another disclosed non-limiting embodiment;

FIG. 8 is a block diagram for an elevator system according to another disclosed non-limiting embodiment;

FIG. 9 is a block diagram of an algorithm for an elevator system according to another disclosed non-limiting embodiment;

FIG. 10 is a block diagram of an algorithm for an elevator system according to another disclosed non-limiting embodiment;

FIG. 11 is a block diagram of an algorithm for an elevator system according to another disclosed non-limiting embodiment;

FIG. 12 is a block diagram for an elevator system according to another disclosed non-limiting embodiment;

FIG. 13 is a block diagram of an algorithm for an elevator system according to another disclosed non-limiting embodiment;

FIG. 14 is a schematic view illustrating operation of an elevator system according to another disclosed non-limiting embodiment;

FIG. 15 is a block diagram for an elevator system according to another disclosed non-limiting embodiment;

FIG. 16 is a block diagram of an algorithm for an elevator system according to another disclosed non-limiting embodiment;

FIG. 17 is a schematic view a human tracker for an elevator system according to another disclosed non-limiting embodiment;

FIG. 18 is a graphical representation of statistical heights for an elevator system according to another disclosed non-limiting embodiment;

FIG. 19 is a block diagram for an elevator system according to another disclosed non-limiting embodiment;

FIG. 20 is a block diagram of a table for an elevator system according to another disclosed non-limiting embodiment;

FIG. 21 is a block diagram of an algorithm for an elevator system according to another disclosed non-limiting embodiment;

FIG. 22 is a graphical representation for passenger tracking from an origin lobby to a destination lobby via in-car tracking;

FIG. 23 is a schematic view of a door arrangement for an elevator system according to another disclosed non-limiting embodiment;

FIG. 24 is a block diagram of an elevator system according to another disclosed non-limiting embodiment; and

FIG. 25 is a schematic view of traffic list generation for a single user; and

FIG. 26 is a block diagram of an algorithm for an elevator system.

DETAILED DESCRIPTION

FIG. 1 schematically illustrates a passenger conveyance system 20 such as an elevator system. The system 20 can include an elevator car 22, an elevator door 24, a lobby call 26, a car-operating panel (COP) 28, a sensor system 30, and a control system 32. It should be appreciated that although an elevator system is disclosed and illustrated as an example herein, other passenger conveyance systems such as mass transit vehicles will also benefit herefrom. It should be further appreciated that although particular systems are separately defined, each or any of the systems may be otherwise combined or separated via hardware and/or software.

The overall amount of travel time a passenger associates with elevator performance may include three time intervals. A first time interval can be the amount of time a passenger waits in a lobby for an elevator to arrive, hereafter the “wait time.” A second time interval can be the “door dwell time” or the amount of time the elevator doors are open, allowing passengers to enter or leave the elevator. A third time interval can be the “ride time” or amount of time a passenger spends in the elevator. The ride time can also include a stop on an intermediate floor to allow passengers to enter and/or exit the elevator which can add to the ride time by at least the door dwell time during the stop.

Various elevator systems can utilize a passenger-initiated input to signal the need for service. For example, input from the lobby call 26 may include a push button, e.g., up, down, or desired destination, to request elevator service. The passenger initiated input (e.g., via a call button) may notify the control system 32 of the presence of a passenger awaiting elevator service. In response, the control system 32 may dispatch the elevator car 22 to the appropriate floor. Optionally, once inside the elevator car 22, the passenger may push a button on the car-operating panel (COP) 28 designating the desired destination, direction, or the like, and then the control system 32 may dispatch the elevator car 22 to that destination.

The control system 32 can include a control module 40 with a processor 42, a memory 44, and an interface 46. The control module 40 can include a portion of a central control, a stand-alone unit, or other system such as a cloud-based system. The processor 42 can include any type of microprocessor having desired performance characteristics. The memory 44 may include any type of computer readable medium that stores the data and control processes disclosed herein. That is, the memory 44 is an example computer storage media that can have embodied thereon computer-usable instructions such as a process that, when executed, can perform a desired method. The interface 46 of the control module 40 can facilitate communication between the control module 40 and other systems.

With reference to FIG. 2, a depth-sensor based passenger sensing system 60 can include a sensor 62 that communicates with a data capture module 64, and a processing module 66. The depth-sensor based passenger sensing system 60 can be a portion of the control system 32, a stand-alone unit, or other system such as a cloud-based system in communication with the control system 32. The data capture module 64, and the processing module 66 can be particular to the sensor 62 to acquire and process the data therefrom. In one example, the sensor 62, through the data capture module 64 and the processing module 66, is operable to obtain depth map data such as the presence of a passenger in a passenger waiting area or lobby H, an estimated time of arrival (ETA) of the passenger, a number of passengers in the lobby H, etc.

The sensor 62, according to one disclosed non-limiting embodiment, can be installed in a lower portion of wall W of the lobby H such as at knee height (FIG. 3). The sensor 62 in this disclosed non-limiting embodiment includes a depth-sensing sensor. It should be appreciated that the term “sensor,” is used throughout this disclosure for any 1D, 2D, or 3D depth sensor, or combination thereof. Such a sensor can be operable in the optical, electromagnetic or acoustic spectrum capable of producing a depth map (also known as a point cloud or occupancy grid) of the corresponding dimension(s). Various depth sensing sensor technologies and devices include, but are not limited to, a structured light measurement, phase shift measurement, time of flight measurement, stereo triangulation device, sheet of light triangulation device, light field cameras, coded aperture cameras, computational imaging techniques, simultaneous localization and mapping (SLAM), imaging radar, imaging sonar, scanning LIDAR, flash LIDAR, Passive Infrared (PR) sensor, and small Focal Plane Array (FPA), or a combination comprising at least one of the foregoing. Different technologies can include active (transmitting and receiving a signal) or passive (only receiving a signal) and may operate in a band of the electromagnetic or acoustic spectrum such as visual, infrared, etc. The use of depth sensing can have specific advantages over conventional 2D imaging. The use of infrared sensing can have specific benefits over visible spectrum imaging such that alternatively, or additionally, the sensor can be an infrared sensor with one or more pixels of spatial resolution, e.g., a Passive Infrared (PIR) sensor or small IR Focal Plane Array (FPA).

Notably, there can be qualitative and quantitative differences between 2D imaging sensors, e.g., conventional security cameras, and 1D, 2D, or 3D depth sensing sensors to the extent that the depth-sensing provides numerous advantages. In 2D imaging, the reflected color (mixture of wavelengths) from the first object in each radial direction from the imager is captured. The 2D image, then, can include the combined spectrum of the source illumination and the spectral reflectivity of objects in the scene. A 2D image can be interpreted by a person as a picture. In 1D, 2D, or 3D depth-sensing sensors, there is no color (spectral) information; rather, the distance (depth, range) to the first reflective object in a radial direction (1D) or directions (2D, 3D) from the sensor is captured. 1D, 2D, and 3D technologies may have inherent maximum detectable range limits and can be of relatively lower spatial resolution than typical 2D imagers. The use of 1D, 2D, or 3D depth sensing can advantageously provide improved operations compared to conventional 2D imaging in their relative immunity to ambient lighting problems, better separation of occluding objects, and better privacy protection. The use of infrared sensing can have specific benefits over visible spectrum imaging. For example, a 2D image may not be able to be converted into a depth map nor may a depth map have the ability to be converted into a 2D image (e.g., an artificial assignment of contiguous colors or grayscale to contiguous depths may allow a person to crudely interpret a depth map somewhat akin to how a person sees a 2D image, it is not an image in the conventional sense.). This inability to convert a depth map into an image might seem a deficiency, but it can be advantageous in certain analytics applications disclosed herein.

The sensor 62 can be, in one example, an eye-safe line-scan LIDAR in which the field-of-view (FOV) can be, for example, about 180 degrees, which can horizontally cover the entire area of a lobby or other passenger area adjacent to the elevator doors 24 (FIG. 2). The output of the LIDAR may, for example, be a 2D horizontal scan of the surrounding environment at a height where the sensor 62 is installed. For an active sensor, each data point in the scan represents the reflection of a physical object point in the FOV, from which range and horizontal angle to that object point can be obtained. The scanning rate of LIDAR can be, for example, 50 ms per scan, which can facilitate a reliable track of a passenger. That is, before application of analytic processes via the processing module 66, the LIDAR scan data can be converted to an occupancy grid representation. Each grid represents a small region, e.g., 5 cm×5 cm. The status of the grid can be indicated digitally, e.g., 1 or 0, to indicate whether each grid square is occupied. Thus, each data scan can be converted to a binary map and these maps then used to learn a background model of the lobby, e.g. by using processes designed or modified for depth data such as a Gaussian Mixture Model (GMM) process, principal component analysis (PCA) process, a codebook process, or a combination including at least one of the foregoing.

The processing module 66 may utilize various 3D detection and tracking processes (disclosed elsewhere herein) such as background subtraction, frame differencing, and/or spurious data rejection that can make the system more resistant to spurious data. Such spurious data can be inherent to depth sensing and may vary with the particular technology employed. For active techniques, where a particular signal is emitted and subsequently detected to determine depth (e.g., structured light, time of flight, LIDAR, and the like) highly reflective surfaces may produce spurious depth data, e.g., not the depth of the reflective surface itself, but of a diffuse reflective surface at a depth that is the depth to the reflective surface plus the depth from the reflective surface to some diffusely reflective surface. Highly diffuse surfaces may not reflect a sufficient amount of the transmitted signal to determine depth that may result in spurious gaps in the depth map. Even further, variations in ambient lighting, interference with other active depth sensors or inaccuracies in the signal processing may result in spurious data.

With reference to FIGS. 4 and 5, in another disclosed non-limiting embodiment, processes 50, 51 for rejection of spurious data are disclosed in terms of functional block diagrams. These functions can be enacted in dedicated hardware circuitry, programmed software routines capable of execution in a microprocessor based electronic control system, or a combination including at least one of the foregoing.

Spurious data rejection process 50 can include multiple steps. First, a depth background can be computed which can be used to segment foreground objects, e.g., a passenger, luggage, etc., from the background, e.g., walls and floors (step 52). The depth data may be three-dimensional. It should be appreciated that the depth data may alternatively be referred to as a depth map, point cloud, or occupancy grid. The depth data may be relatively “noisy.”

A multi-dimensional-based approach can be used to model the depth background. 2D imager background modeling approaches can be insufficient for depth background modeling. For example, the depth uncertainty can be an analytical function of range, the depth data error can be discontinuous (or not continuous), and the depth distribution can be non-Gaussian as compared to typical 2D image data (e.g., not able to be represented by a continuous probability distribution), or a combination comprising at least one of the foregoing which can render the 2D imager background modeling insufficient for depth background modeling.

Second, after background subtraction and foreground detection, morphological operations may be used to filter isolated small foreground regions (e.g., which can be “noise”) and to segment moving objects, called blobs, for further analysis (step 54). This analysis can be performed in 3D. However, 3D extension of 2D connected components may be inappropriate since the 3D data still has self-occlusion, e.g., “shadows” in an occupancy grid. An approach to filtering may include a process of extending 2D connected components to include an “unknown” category in the occupancy grid for 3D morphological filtering.

The morphological filtering is further explained in reference to FIG. 5. In 3D morphological filtering 51, accounting for occlusion can be performed in multiple steps (e.g., as shown in FIG. 5 which can include four successive steps). A 2D foreground object mask can be computed by depth background subtraction (step 53). Foreground objects within the mask can be at any depth, and partially or completely occlude objects therebehind.

Size filtering can be performed on the mask as a function of range that may remove objects below a predetermined size (step 55). Any “nearby” mask regions are connected using 2D connected components that potentially merge objects with distinct depths (step 57). The objects can then be segmented in 3D based on depth discontinuity (step 59). It is possible that some objects after depth discontinuity segmentation will be relatively small, e.g., someone almost entirely occluded by another person will appear as a small blob. This approach can be used to track such small objects so they can be classified rather than filtering them out.

In reference to FIG. 4, with the sensor calibration result disclosed elsewhere herein, the foreground blobs can be transformed to 3D world coordinates, and their actual heights and volumes can be estimated (step 56). Morphological filtering can be used to remove a blob if selected characteristics, such as height, width, aspect ratio, volume, acceleration, velocity, and/or other spatiotemporal characteristics are outside a detection threshold (e.g., dynamically calculated threshold, static threshold, or the like).

Geometric filtering can be applied to further remove spurious blobs outside the scene boundary (step 58). The depth background defines a 3D scene boundary of the environment. A blob representing a real object should be within the 3D boundary. That is, if a blob's depth is larger than the depth of the corresponding location of the depth background, then the blob is outside of the 3D boundary and can be removed, e.g., a blob detected from reflective surfaces such as a mirror. Passengers or other moving objects can then be readily detected by a background subtraction technique with high robustness to illumination change, shadows, and occlusion, to thereby provide accurate passenger data. To further increase detection robustness, temporal information can alternatively or additionally be utilized, e.g., by tracking

Passenger tracking may also be based on the binary foreground map and a method such as a Kalman filter to track passengers and estimate the speed and moving direction thereof. Based on detection, tracking, and counting, passenger data such as the presence of a passenger in the lobby, an estimated time of arrival (ETA), and a number of waiting passengers can be obtained. Such passenger data can then be used to, for example, improve lobby call registration and elevator dispatching.

For example, the detection, tracking, and counting, facilitated by the depth-sensing device may facilitate registering a hall call for an approaching passenger, particularly at a terminal floor; opening the car doors for an approaching passenger if a car is already at the floor; prepositioning a car based on an approaching passenger; and/or generating multiple hall calls based on the number of approaching passengers such as when multiple passenger essentially simultaneously leave a seminar.

In another disclosed non-limiting embodiment, the sensor 62 can be installed with a FOV toward the elevator doors 24 and the lobby H. Such a position facilitates continuous monitoring of the lobby H such that information may be obtained far more completely and further in advance of that which is available by a sensor in car which can sense the lobby H only when elevator doors are open. Similar processes may alternatively or additionally be employed as above, but specifically designed and trained for the 3D depth map data.

With reference to FIG. 6, in another disclosed non-limiting embodiment, a sensor system 30B may include a passenger tracking system 70 within the elevator car 22 to facilitate operation of the elevator doors 24. The passenger tracking system 70 may include a sensor 72 that communicates with a data capture module 74, and a data processing module 76 that communicates with the data capture module 74 and a door control module 78. The passenger tracking system 70 can be a portion of the control system 32, a stand-alone unit, or other system such as a cloud-based system in communication with the control system 32.

Passenger tracking system 70 can be specially designed to utilize depth map data. Tracking may be regarded as a Bayesian Estimation problem, i.e., what is the probability of a particular system state given the prior system state, observations, and uncertainties. In such tracking, the system state may be the position of the tracked object, e.g, location and, possibly, velocity, acceleration, and other object characteristics, e.g., target features as disclosed elsewhere herein. The uncertainties are considered to be noise. Depending on what simplifying assumptions are made for mathematical tractability or efficiency, the Bayesian Estimation becomes the variants of Kalman Filtering (assumption of Gaussian additive noise) or the variants of Particle Filtering (assumption of non-Gaussian noise). In 2D and 3D object tracking, where there are many pixels/voxels on target, the system state often includes a target representation that includes discriminative information such as color descriptors (2D only), shape descriptors, surface reflectivities, etc. The possible target models are sensor and application specific.

One disclosed non-limiting embodiment of depth data tracking for passenger tracking system 70 is based on Kalman Filtering and the system state includes five (5) variables: x, y, h, vx and vy, which represent target's real world x and y position, height, and velocities in the x and y directions. The tracking process comprises two steps: prediction and update. A constant velocity model, or other types of model such as random walk or constant acceleration models, can be applied for prediction and, through the model, targets (their states) in a previous depth map can be transferred into the current depth map. A more complex model can be used if needed. In the update step, first all the targets in the current depth map are detected with an object detection process, i.e., depth based background subtraction and foreground segmentation, as disclosed elsewhere herein, then the detected targets are associated with predicted targets based on a global optimal assignment process, e.g. Munkres Assignment. The target's x, y, and h variables are used as features for the assignment. The features (x, y, and h) are effective to distinguish different targets for track association.

For the predicted target that has an associated detected target, the target system state can be updated according to the Kalman equation with the associated detected target as the observation. For a predicted target that has no associated detected target, the system state may stay the same, but the confidence of target will be reduced, e.g., for a target that is already going out of the field of view. A track will be removed if its confidence falls below a predetermined or selected value. For a detected target that has no associated predicted target, a new tracker will be initialized.

Other tracking approach like Particle Filtering may alternately or additionally applied which will be more robust in cases where a target abruptly changes its velocity. The Kalman approach, requires relatively little computational cost and may therefore be more suitable for real-time application.

In this embodiment, the sensor 72 may be installed at the top of an elevator car 22 with a FOV downward and toward the elevator doors 24. The sensor 72 can thereby be operable to perceive passengers in the car 22 and also, when the elevator doors 24 are open, may be operable to perceive passengers in the lobby H. The data capture module 74 captures data, e.g., 3D depth map data, from the sensor 72. When the door control module 78 sends a signal to open the doors 24, for example after elevator 22 stops at a floor, the door control module 78 may also trigger a signal for the data capture module 74 to capture sensor data. In one embodiment, passenger tracking may only be active when the doors 24 are open and/or may be inactive when the doors 24 are closed. In another embodiment, the data capture module 74 may continuously process data and thereby detect when the doors 24 are open, eliminating the need for this information from the door control module 78, such that the door control module 78 is free of the door position information.

With reference to FIG. 7, in another disclosed non-limiting embodiment, process 80 for detecting objects in the elevator car 22 and in the lobby H is disclosed in terms of functional block diagrams and it should be appreciated that these functions can be enacted in either dedicated hardware circuitry or programmed software routines capable of execution in a microprocessor based electronics control embodiment

The data capture module 74 communicates the data to the data processing module 76 to detect objects in both in the elevator car 22 and in the lobby H (step 82). The object detection may include foreground detection, as disclosed elsewhere herein, and passenger detection using computer vision processes for depth data. Passenger detection may be achieved by human model fitting, e.g., by using a Deformable Part Model, and classification, where the detection and classification can be specially trained for the FOV and 3D depth map data.

Next, the detected objects will be tracked to obtain their moving speed and direction (step 84). The speed and direction can be in the sensor coordinate system, and/or through sensor calibration, in the world coordinate system as further disclosed elsewhere herein. If detected passengers are just standing in the elevator car 22 or the lobby H, their moving speed is 0, which indicates that these passengers are not immediately going to board or exit the elevator car 22.

For depth map based tracking, various processes can be used as disclosed elsewhere herein. Particular motion detection functions, for example, using Bayesian Estimation, determines if a passenger is just shifting position, or is intentionally moving toward the doors 24 from within the car 22. This is particularly beneficial to specifically identify if a passenger at the rear of a crowded car 22 who wishes to exit.

With the information of moving speed and direction of passengers both in the elevator car 22 and in the lobby H, the elevator doors 24 may be respectively controlled (step 86). For example, if numerous passengers are boarding or exiting, the elevator doors 24 can be controlled to remain open relatively longer than normal and then be closed promptly after all the passengers have boarded or exited. Conversely, if there are no passengers waiting to board or exit, the elevator doors 24 can be controlled to close relatively more quickly than normal to reduce passenger wait time and improve traffic efficiency.

With reference to FIG. 8, in another disclosed non-limiting embodiment, a sensor system 30C may include an unoccupied car determination system 90 to facilitate determination as to whether the elevator car 22 is unoccupied, as an unoccupied elevator car 22 may be advantageously moved from five to ten times faster than an occupied elevator car 22 or moved in other ways not comfortable to passengers and/or within code restrictions.

The unoccupied car determination system 90 may include a sensor 92 that communicates with a data capture module 94, and a data processing module 96 that communicates with the data capture module 94, and a car status module 98. The unoccupied car determination system 90 can be a portion of the control system 32, a stand-alone unit, or other system such as a cloud-based system in communication with the control system 32. The unoccupied car determination system 90 may additionally include a load sensor 100 in communication with the data capture module 94 and the data processing module 96.

With reference to FIG. 9, in another disclosed non-limiting embodiment, process 110 for determining elevator car 22 is unoccupied is disclosed in terms of functional block diagrams and it should be appreciated that these functions can be enacted in either dedicated hardware circuitry or programmed software routines capable of execution in a microprocessor based electronics control embodiment

The load sensor 100 can be operable to sense a current load weight of the elevator car 22, and may further determine if the sensed load weight is less than a preset threshold. The load sensor 100 may further trigger a signal to the data capture module 94 to indicate that there is a high probability (e.g., greater than 80%, or, 90%, or 95%) that the elevator car 22 is empty (step 111). Should the data capture module 94 receive an empty signal from the load sensor 100, the data capture module 94 will pass the current depth map sensor view (step 112) to the data processing module 96 for further confirmation that the car 22 is empty via application of data capture processes (step 113). The load sensor 100, however, may be a relatively course sensor and may tend to drift in accuracy over time. If the load sensor 100 is sufficiently inaccurate, it may be desirable that data capture module 94 run continuously rather than being triggered by load sensor 100.

Utilization of a 3D depth-sensing sensor as the sensor 92 facilitates confirmation of an empty car by in-car foreground detection or passenger detection, with various analytics processes modified to operate with the depth data as disclosed elsewhere herein. The 3D depth-sensing sensor can facilitate accurate identification of passengers, heretofore undetectable objects (e.g., such as briefcases, umbrellas, luggage and the like) or a combination comprising at least one of the foregoing. Such identification can be accompanied by an audible notification, for example, “PLEASE REMEMBER YOUR BELONGINGS.” It should be appreciated that other appropriate alerts may alternatively be provided.

An output of the data processing module 96 can include a signal indicating whether the car 22 is confirmed unoccupied (step 114). With this signal, elevator standby mode, unoccupied movement modes, and/or multicar functions can be accurately applied (step 120).

A signal from the data processing module 96 may additionally or alternatively be an input to the load sensor 100 for re-calibration to maintain the accuracy thereof (step 116). For example, upon confirmation of an empty car 22 via the sensor 92, the load sensor 100 can be recalibrated. In particular, if the car 22 is confirmed empty, the sensed load weight by the load sensor 100 may be set to zero, or, the difference may be used to adjust the offset in the load sensing equation.

In another disclosed non-limiting embodiment, an unoccupied car management system 120 may be utilized to facilitate operation of elevator car calls, car dispatching, and car motion, which are managed based on the determination of whether the elevator car 22 is unoccupied. More specifically, the unoccupied car management system 120 can be utilized to cancel all remaining car call(s) when the car 22 is unoccupied, balance the number of passengers between cars 22, direct passengers to specific cars 22, and/or change a motion profile to provide an enhanced passenger experience, improved dispatching, and/or increased throughput.

With reference to FIG. 10, in another disclosed non-limiting embodiment, a sensor system 30D may include an elevator monitoring system 130 to facilitate detection of objects and/or a trapped passenger within the elevator car 22. The elevator monitoring system 130 may include a sensor 132, such as a 3D depth-sensing sensor. Utilization of the 3D depth-sensing sensor readily overcomes restrictions inherent in 2D imaging, such as illumination changes, and occlusion as disclosed elsewhere herein.

The sensor 132 communicates with a data capture module 134, and a data processing module 136 that communicate with the data capture module 132 and a rescue center module 138. The system 130 can be a portion of the control system 32, a stand-alone unit, or other system such as a cloud-based system in communication with the control system 32.

An elevator operation monitoring module 140 may also communicate with the data capture module 134. The elevator operation monitoring module 140 monitors the status of the elevator system 20 and if there is any malfunction, the elevator operation monitoring module 140 may trigger the sensor 132. The data capture module 134, when triggered, will capture one or more depth maps from the sensor 132 for communication to the data processing module 136. The data processing module 136 receives the 3D depth map data and may apply various analytics processes to determine whether there are any passengers or objects in the elevator car 22 as disclosed elsewhere herein. It is also possible for data capture module 134 to run continuously without trigger from elevator operation monitoring module 140.

In a malfunction such as a power outage, a battery backup 142 may be provided for continued 3D sensing and processing. The continued 3D sensing and processing may thus be performed in a manner to conserve battery life by judicious use under loss-of-power conditions.

With reference to FIG. 11, in another disclosed non-limiting embodiment, a process 150 for operation of the elevator monitoring system 130 is disclosed in terms of functional block diagrams and it should be appreciated that these functions can be enacted in either dedicated hardware circuitry or programmed software routines capable of execution in a microprocessor based electronics control embodiment.

The process 150 provides for initial data processing to extract a foreground region based on depth background subtraction (step 152). A depth background model may be generated a priori and updated as required. Generation of the depth background model may be based on, for example, a codebook process. The depth background subtraction with an active 3D sensor is advantageously robust to illumination changes because the transmitted signal is used to determine depth.

Next, a foreground region is segmented based on the depth map and spatial information (step 154). In this step, regions corresponding to different passengers or other objects such as luggage can be segmented from the background. Finally, each segmented region is checked with a human shape model to determine whether the depth data is of a human (step 156). In one example, the depth-based human shape model can be a Deformable Part Model to increase robustness to occlusion. The part based model may also be trained for the depth data and sensor FOV to increase accuracy. Multiple models may be created for different passenger poses, like standing, sitting, and lying down. The results are then output to indicate, for example, a number of passengers or objects (step 158). The data processing module 136 thus not only outputs information as to whether there is a trapped passenger in the elevator car 22, but also the number of passengers that are trapped for communication to the rescue center module 138 to facilitate an appropriate rescue response.

With reference to FIG. 12, in another disclosed non-limiting embodiment, a sensor system 30E can include a special loading system 160 to facilitate the detection of special loading conditions. Special loading conditions, as defined herein, may include loading any object other than a human passenger and any loading that takes a relatively longer time than normal, e.g., for wheelchairs, the elderly, passenger with large luggage carriages, etc.

With the detection of special loading conditions, the special loading system 160 improves passenger experience and traffic performance. For example, an elevator dispatching system of the elevator control 32 can assign an elevator car 22 with sufficient free space and the elevator door control 78 (FIG. 6) can hold the elevator doors 24 open longer to accommodate slowly moving passengers or other special loading conditions such as large luggage (which might even take multiple trips in and out of the car 22 to load), service carts, or even an autonomous vehicle.

The special loading system 160 may include a sensor 162 (installed in the lobby H or at a remote kiosk) to view a passenger who desires an elevator car 22 through analytics disclosed elsewhere herein. Utilization of a 3D depth-sensing sensor as the sensor 162 overcomes the aforementioned fundamental limitations of 2D imagers.

The sensor 162 communicates with a data capture module 164, that communicates with a data processing module 166 that communicates with the data capture module 164 and a special loading detection module 168. The special loading detection module 168 may also receive information from a classifier module 170 and communicates with an elevator control system 172. The system 160 may be a portion of the control system 32, a stand-alone unit, or other system such as a cloud-based system in communication with the control system 32.

With reference to FIG. 13, in another disclosed non-limiting embodiment, a process 180 for operation of the special loading system 160 is disclosed in terms of functional block diagrams and it should be appreciated that these functions may be enacted in either dedicated hardware circuitry or programmed software routines capable of execution in a microprocessor based electronics control embodiment.

Initially, in response to detection of a passengers desire to summon an elevator car as disclosed herein (step 182), the special loading process 180 will acquire depth map data from the sensor 162 (step 184) and then the depth map data is communicated to the data processing module 166 (step 186). The data processing module 166 then operates to segment foreground objects from the background as disclosed elsewhere herein (step 168). This facilitates focus on foreground objects and removes the background influence. Various background modeling and subtraction processes suitably modified and trained on depth data can be applied to segment foreground objects as disclosed elsewhere herein.

After foreground objects have been segmented, a spatial, or spatiotemporal classification approach facilitates detection of whether these foreground objects constitute a special loading condition (step 190). For the general case of a special loading condition, it may be difficult to manually define useful features for all possible special loading conditions and to encompass the large amount of possible variation in the sensor data and environment. Therefore, the special loading process 180 may be trained to learn features or feature hierarchies of special loading conditions that are different from normal loading.

With such automatically learned features, special loading detection may be effectively classified by the classifier module 170 (step 192). The classification step 190 may be, for example, feature learning and classification such as via a Deep Learning Network or Sparse Learned Dictionary. Other classifiers as known in the art may be advantageously employed. The classifier training may, for example, be performed offline for various objects, and for real-time detection, the object detection can be specifically tailored based on predetermined requirements. This permits the special loading system 160 to be more adaptable for various special loading detection needs as well as readily provide scalability.

Further, the detected special loading condition may be mapped to the floor area adjacent to the elevator. Such map mapping may include, for example, distances from a call button kiosk, and actual moving speed, so that the elevator control system 172 may be tailored for the particular dispatching decisions and motion/door control (step 194). For example, this may be performed in one step. For example, the classifier, on recognizing each special loading condition, directly outputs the learned needed floor area and actual moving speed. In an alternative embodiment, this may be performed in two steps, first the special loading condition is classified then subsequent processing of the sensor data is conditioned on the special loading condition, to compute, for example, floor area, speed, or other information.

In one example, and with reference to FIG. 14, a special loading condition such as a passenger with a luggage cart “L” who presses a button at a kiosk “K” may be tracked to obtain the moving speed “S,” to thereby provide an ETA (estimated time of arrival) from the distance “D” to the elevator car 22. The ETA can thus be used for appropriate dispatching and door control with adequate dwell time.

With reference to FIG. 15, in another disclosed non-limiting embodiment, a sensor system 30F may include an auto-calibration system 200 to facilitate accurate determination of key calibration parameters rather than relying on an installer's labor, skill, and additional equipment.

The auto-calibration system 200 may include a sensor 202 such as a 3D depth-sensing sensor that can perform other functions such as those disclosed elsewhere herein. The sensor 202 may be deposed within an elevator car 22 or within an elevator lobby H. The sensor 202 communicates with a data capture module 204, and data capture module 204 communicates with a data processing module 206 and may communicate with an auto-calibration process 210. Data processing module 206 may also communicate with auto-calibration process 210. The auto-calibration system 200 can be a portion of the control system 32, a stand-alone unit, or other system such as a cloud-based system in communication with the control system 32.

The data processing module 206 may include a process 210 (FIG. 16) for operation of the auto-calibration system 200. In another disclosed non-limiting embodiment, an process 210 for auto-calibration of sensor 202 is disclosed in terms of functional block diagrams and it should be appreciated that these functions may be enacted in either dedicated hardware circuitry or programmed software routines capable of execution in a microprocessor based electronics control embodiment

Initially, at least one measurement in the sensor coordinate system may be determined by the system 200 of a moving object in the field of view using background subtraction and foreground segmentation as disclosed elsewhere herein. Next, data to establish a mathematical relationship, such as a transform matrix which captures the calibration information, is recorded in the sensor coordinate system (u,v,d) pertaining to the movement of passenger through the world coordinate (x,y,z) space (step 214).

Next, suppositions about the scene geometry, e.g., the floor is flat, a passenger stands upright on the floor, a passenger does not change height, doors are orthogonal to floors, etc., are utilized for comparison of the recorded sensor coordinate system data with statistical data about passenger's heights (FIGS. 17 and 18; step 216). Upright passengers are detected by, e.g., connected components satisfying a simple aspect ratio threshold. Once enough upright passengers are detected, the floor plane can be determined and for each floor location the distribution of passenger's heights can be computed.

From predetermined knowledge of the distribution of passenger's heights (FIG. 18), the Z-axis can be calibrated (step 218). This Z-axis calibration from the distribution of passenger's heights can be considered a system identification problem where the requisite persistent and sufficient input is the size and motion of passenger through the field of view. The recorded height data can be collected during a setup period, maintained over a time period, and/or be subject to a forgetting factor.

From the apparent height as a function of range, or voxel aspect ratio, the (X, Y) axes can then be calibrated based on the Z-axis calibration (step 220). The sensor coordinate data may then be mapped into the world coordinate system of absolute or ‘metric’ units (step 222).

To further facilitate recognition of passenger's intention such as approaching, leaving, or passing by, the position of the elevator doors 24 may also be determined. The position of the elevator doors 24 may be determined based on various methods, such as detecting the location where passengers appear, disappear, depth change detection, depth of an elevator car, elevator door horizontal movement, and shape recognition. That is, the deduction of scene geometry may also be extended to locate doors, the edge of the field of view, etc. Further, any of these techniques can be combined with installer input, where convenient. The method can monitor the convergence of the matrix mathematical relationship estimation of the calibration information to determine when sufficient accuracy has been achieved.

In an alternative embodiment, the floor plane and the elevator door position can be estimated in the sensor coordinate system (u,v,d) and all tracking can be performed in this coordinate system. In this case the estimated arrival time can be learned by timing passenger's tracks, e.g., as a function of an empirical map.

In an alternative embodiment, the position of the elevator doors 24 can be established at the time of commissioning by having the installer follow a standard operating procedure whereby a calibration rig is positioned with respect to the elevator door 24. For example, the rig can be positioned flush with the center of the elevator doors 24 and oriented perpendicularly from the elevator doors 24. Additional features can be utilized to indicate each of the calibration points on the calibration rig with uniquely identifiable features, such as the use of colors, shapes or patterns such as QR codes.

In another alternative embodiment, other areas of interest besides the elevator doors 24 can be identified. For instance, the location of passenger fixtures such as the COP 28, destination entry kiosks, the location of escalator entry/exit landings, the location of turnstiles/access control devices, room entrances, doorways, etc. can be specified.

With reference to FIG. 19, in another disclosed non-limiting embodiment, a sensor system 30G may include a passenger tracking system 230 to detect a passenger in the lobbies H and the elevator cars 22 to link all the information together to generate a traffic list (FIG. 20) for each individual in a building for various applications. For example, traffic pattern prediction based on the traffic list information can focus on the whole building level passengers' traffic information instead of single zones or multiple zones. The traffic list information provides more detailed information about passenger's behaviors in the building, and also can be used for various applications in addition to elevator control and dispatching.

The passenger tracking system 230 may include a plurality of sensors 242 that communicate with the elevator system 20 via the control system 32. In one example, a sensor 242 is located in each lobby H and each elevator car 22. Alternatively, a sensor 242 is only located in each elevator car 22. The sensors 242 can be 2D imagers, 3D depth sensing sensors, or any combination thereof.

With reference to FIG. 21, in this disclosed non-limiting embodiment, a process 250 for operation of the passenger tracking system 230 is disclosed in terms of functional block diagrams and it should be appreciated that these functions can be enacted in either dedicated hardware circuitry or programmed software routines capable of execution in a microprocessor based electronics control embodiment.

A traffic list (FIG. 20) contains detailed information of each individual passenger that has used an elevator, such as arrival time, origin lobby, destination lobby, etc. To generate the traffic list, each individual passenger is tracked from an initial point in a lobby, to when the passenger leaves a destination lobby, as well as through an in-car track between the origin lobby and the destination lobby.

To generate the tracking list, the sensors 242 may collect passenger information based on various passenger detection and tracking processes as disclosed elsewhere herein. Initially, each person can be detected and tracked when they appear in a lobby or upon exit from an elevator car 22 (step 252). If sensor 242 is a 3D depth sensor, the detection and tracking process disclosed elsewhere herein can be applied. If sensor 242 is a 2D imaging sensor, “integral channel features” may be computed by multiple registered sensor channels via linear and/or non-linear transformations of input images, then a passenger detection model based on the “integral channel features” can be learned by boosting, which offers a robust and fast approach for learning given a large number of candidate features, and results in fast detectors when coupled with cascade classifiers. This detection and tracking process may, for example, be based on 2D RGB video.

In one embodiment, two trackers are designed to track one target: a head-shoulder tracker via online boosting, and a body tracker based on particle filtering. A spatial constraint may also be utilized to combine the two trackers and a boosted online classifier may be maintained for occlusion and disappearance judgment.

For example, when a person enters an elevator car, in-car detection and tracking is triggered (step 254). That is, each person is tracked while within the car, and while the person is in the destination lobby (step 256). For the in-car track, the sensor is looking relatively downward, so passengers will look similar as only the head and shoulder appear in the field of view. This may complicate tracking when passengers are crowded therein. To address this complication for a 2D image sensor, each passenger's head is first detected by, for example, a circle-Hough transform, then optical flow based motion estimation is developed to filter out motionless candidates and adjust a head detection result to enclose each passenger. To further facilitate the in-car tracking, a motion-guided particle filtering approach may combine two features, e.g., an HSV color histogram and an edge orientation histogram, and may utilize an effective model updating strategy based on motion estimation.

In order to maintain the association of a person tracked in one sensor's FOV with the same person tracked in another sensor's FOV, lobby/hallway tracking and in-car tracking are associated as a passenger moves from a lobby/hallway into a car and vice versa. The 2D image sensor hand off association problem may utilize visual surveillance and techniques for both overlapping and non-overlapping fields of view and for both calibrated and non-calibrated fields of view. In one example, a descriptor, e.g. a feature vector, may be computed using color or shape and then this descriptor is used to compute the correct association across the different fields of view.

In 3D tracking, the common 2D descriptors such as color and 2D projected shape (e.g., 2D gradients) are not available. As such, a 3D descriptor, i.e., a surface reflectivity histogram, a Histogram of Spatial Oriented 3D Gradients (HoSG3D), etc. may be used. The HoSG3D is different than the 2D HoG3D descriptor because the 3rd dimension is spatial, while in HoG3D, the 3rd dimension is time. However, passenger shape passenger may be sufficiently similar that using only HoSG3D may not be sufficiently discriminative to unambiguously hand a track from one sensor to another.

In another embodiment, the natural serialization of passengers entering an elevator car may be used to associate tracks, e.g., the first lost track in one sensed volume is associated with the first newly acquired track in the other sensed volume, etc. This, too, may not be sufficiently accurate since passengers might exchange order while out of both sensed volumes, and the strict serialization of car entry may not occur. To ensure accuracy, overlapping, calibrated sensed volumes provide better performance since the position of an object in the overlapping sensed volumes can be known to be at the same spatial position.

In another embodiment, a combination of the above techniques, or can be used. When the multiple techniques provide conflicting information on the correct track association, the ambiguity may be resolved by solving a Bayesian Estimation problem to maximize the probability of correct association given the observations and uncertainties. It will be recognized that other mathematical formulations of the association problem are possible. For tracking hand over between a sensor 242A located in a lobby and a sensor 242B located in an elevator car 22, a graph based optimization approach may be utilized (FIG. 22). The graph based optimization approach, in one example, includes three layers of nodes, representative of tracking in the origin lobby, tracking in-car, and tracking in a destination lobby.

The tracking hand over is then solved by a graph-based optimization 260 to find overall best paths. The example graph-based optimization 260 may be weighted by order and time difference. That is, as passengers typically enter and leave the car in a sequential manner, filtering thereof is readily achieved to provide best paths by weights and similarity of nodes.

With reference to FIG. 23, if the elevator doors 24 are opening, then the vertical edges of door 24, e.g., as detected by a line-based Hough Transform, will traverse regions 1, 2 and 3 in order, and if the door is closing, the door edges will traverse regions 3, 2, 1 in order. The position of the elevator doors 24 may also be confirmed via a sensor 242B located in elevator car 22 or a sensor 242A located in lobby H with a view of elevator doors 24 to confirm the doors are opening, opened, closing, closed. That is, the elevator door status may be input from elevator controller 32 or may be detected by sensor 242A/242B to improve the performance and efficiency of a tracking hand over solution. For example, the tracking hand over need only be performed when the elevator door is open. It should be appreciated that other conveyances will also benefit herefrom.

With reference to FIG. 24, in another disclosed non-limiting embodiment, a sensor system 30H may include a fusion based passenger tracking system 270 to predict the potential movement of a passenger, then adaptively assign elevator cars based on instantaneous needs so as to bring more efficiency and convenience to elevator passengers in the building. An elevator system with a complete, accurate traffic list (FIG. 20) can predict the potential movement of passengers on, for example, an hourly, daily, weekly, etc. basis and use the elevators based on the anticipated traffic to increase efficiency and convenience to elevators passengers. In order to achieve the robust traffic list generation, a fusion based traffic list generation method is provided.

Referring now to FIG. 25, the fusion based passenger tracking system 270 may include a plurality of security sensors 280 a-280 n that communicate with the elevator system 20 via the control system 32. That is, the sensor data from the security sensors 280 essentially provides data to the control system 32 to include, but not be limited to, facial recognition, badge identification, fingerprints iris data, security card information, etc. In areas without surveillance coverage or where the analytics processes may not perform well, the additional security sensors can recognize the person and then, using sensor fusion, close the gaps in the traffic list to make the whole process more robust. In any instance where identity is associated with a passenger, the identity and associated passenger tracking data is maintained in a way that preserves privacy by using encryption, authentication, and other security measures.

The sensor fusion may be performed by Bayesian Inference, but in alternative embodiments may be performed by any well-known technique. With the security information and traffic history data, the patterns for a person moving in the building may be determined to understand normal behavior as well as improve elevator service. In this disclosed non-limiting embodiment, the traffic list contains detailed information of passengers using the elevator sensors 284, as well as security data from various security sensors 280. The data from various sensors are fused and communicated to the elevator system 20 via the control system 32. The identification information is linked with this person's visual description features, so the whole traffic list under different imager's or sensor's views will have the ID information. That is, the passenger traffic list is based on coordinating (“hand-over”) between lobby and car tracking results. The fused data may then be used to facilitate elevator dispatching.

Hand-over rules may be pre-defined, such as a first-in and first-out rule. For a first-in and first-out rule, when the lobby sensor and the car sensor operate simultaneously for target tracking in the same region, and one passenger is moving from the lobby to board the car, then this out-of-lobby-into-car information may be used to link the tracker from the lobby to the tracker in the car. When the passenger leaves the car and goes to the lobby, a similar rule (out-of-car-into-lobby) may be applied to link the tracker in the car with the tracker in the lobby.

In one example, security sensors recognize a particular passenger and his security data is shared with all the other sensors to link the tracking results with that passenger's ID. Second, in some areas, where the security sensors are not installed, the security credential information may be utilized to continue tracking that passenger's presence in the building and in this way continue the traffic list generation for that passenger. Additional information derived from one imager's or sensor's view may also be shared with other imager(s) or sensor(s) to further improve track association across non-overlapping views.

The traffic lists for a single passenger may be combined over time, with time as a parameter, using Bayesian Inference for a probabilistic prediction of the passenger's intended destination. Such a system could learn that passenger A always goes to Floor N early in the morning, typically to Floor C (the cafeteria) at noon, and always goes to the Parking Garage in the late afternoon.

Further, the traffic lists for multiple passengers can be combined over time, with time as a parameter, again using Bayesian Inference. Such a system facilitates statistical distribution determination of elevator usage for the entire building during a typical day as well as weekend days, holidays, etc. This information could be used to pre-assign cars to runs (even purposefully skipping floors), for efficient parking, dispatching cars, etc.

Given the information of the traffic lists, the elevator optimization is achieved by techniques for real-time solution of an optimization problem. The traffic lists information can also be utilized for other elevator related applications such as elevator daily load estimation to provide one accurate energy report for future energy saving, elevator system diagnostics based on abnormal traffic list information, modernization value propositions, and so on.

With reference to FIG. 26, in another disclosed non-limiting embodiment, a process 300 may further utilize the elevator sensors 284, as well as the security data from the various security sensors 280 to recognize a particular passenger for passenger convenience, to optimize elevator operations, improve operations and/or for various security purposes. The process 300 permits multiple passengers to be simultaneously allowed in the car without confusion of destinations.

Initially, a passenger may be recognized in an origin lobby such as while approaching an elevator (step 302). The elevator sensors 284 can be simultaneously operable, disparate-view, multi-sensor recognition, particularly combining 2D imagers; and 1D, 2D, or 3D depth sensors as well as alternative or combinations thereof, i.e., 2D/3D. Again, the data from various imagers and depth sensors are fused and communicated to the elevator system 20 via the control system 32. The passenger may be recognized by, for example, something they know, e.g., a password, something they have, e.g., a token or ID card, and/or by something they are, e.g., a unique biometric. In one biometric example, face recognition is both relatively inexpensive and well developed.

Next, a call for a predefined destination floor is registered based on the recognized person (step 304). The determination of the desired floor can be prerecorded by the person or can be automatically learned by traffic analytics such as via a traffic list. Even with recognition and tracking capabilities, a pattern for the particular individual may not be automatically discernable without statistical analysis capable of ignoring outliers, i.e., due to occasional non-typical elevator usage. In one embodiment, Robust Principle Components Analysis (RPCA) for this outlier-ignoring learning is utilized. In another embodiment Bayesian Inference can be utilized.

Next, a particular elevator car is assigned for the person, and the person is directed to the appropriate car (step 306). Various assignments can be based on particular identification, common usage, etc. such that a particular passenger is always directed to the closest car, fastest car to his or her destination, etc.

The assigned car can be further provisioned with an alert if the person boards the wrong car or is heading towards the wrong car. The alert can be based upon tracking the passenger into the car, however, the alert need not be a request to exit as such a request may result in a negative customer experience. The alert, in one example, can be used to deregister the passenger in the previous car and register the intended destination floor in the new car 22. The elevator dispatching can then be re-optimized in real-time, including redirecting the passenger through sky lobbies, to provide a desired throughput and customer experience.

Next, the passenger may be tracked from the lobby, into the car, during transit, then through the destination lobby as discussed above. In some instances, while the passenger is tracked within the car, selection of a different destination can be identified. For example, while tracking the passenger to correspond with the destination, analytics that the person has pushed a button to change destination, and temporally correlated information from the car controller as to which button was pressed can be used to identify the change in destination. Once the change in destination is identified, throughput optimization can be performed thereby.

The process 300 may also alert a passenger if, for example, the passenger mistakenly exits at a destination different than that registered for that particular passenger (step 308). In one embodiment, it can be desirable to alert the passenger before the passenger actually mistakenly exits. The process 300 may thereby infer the intent or initial movement of the passenger toward the doors via track analysis, e.g., movement towards the front of the car. The customer alert may be by audible voice signal. Alternatively, for security purposes, the alert may silently notify security personnel or systems and track the passenger.

The elements disclosed and depicted herein, including in flow charts and block diagrams throughout the figures, imply logical boundaries between the elements. However, according to software or hardware engineering practices, the depicted elements and the functions thereof may be implemented on machines through computer executable media having a processor capable of executing program instructions stored thereon as a monolithic software structure, as standalone software modules, or as modules that employ external routines, code, services, and so forth, or any combination of these, and all such implementations may be within the scope of the present disclosure.

It should be appreciated that relative positional terms such as “forward,” “aft,” “upper,” “lower,” “above,” “below,” “bottom”, “top”, and the like are with reference to the normal operational attitude and should not be considered otherwise limiting.

It should be appreciated that like reference numerals identify corresponding or similar elements throughout the several drawings. It should also be appreciated that although a particular component arrangement is disclosed in the illustrated embodiment, other arrangements will benefit herefrom.

Although the different non-limiting embodiments have specific illustrated components, the embodiments of this invention are not limited to those particular combinations. It is possible to use some of the components or features from any of the non-limiting embodiments in combination with features or components from any of the other non-limiting embodiments.

Although particular step sequences are shown, disclosed, and claimed, it should be appreciated that steps may be performed in any order, separated or combined unless otherwise indicated and will still benefit from the present disclosure.

The foregoing description is exemplary rather than defined by the limitations within. Various non-limiting embodiments are disclosed herein, however, one of ordinary skill in the art would recognize that various modifications and variations in light of the above teachings will fall within the scope of the appended claims. It is therefore to be appreciated that within the scope of the appended claims, the disclosure may be practiced other than as specifically disclosed. For that reason the appended claims should be studied to determine true scope and content. 

1-27. (canceled)
 28. A method of generating a traffic list comprising: detecting a passenger entering an elevator from a first lobby using 3D sensor data from one or more sensors positioned within the elevator; receiving time data to establish a timestamp associated with the arrival of the passenger; receiving floor position data associated with the floor position of the first lobby at a time proximate to when the passenger is detected entering the elevator; tracking the passenger movement while within the elevator using 3D depth sensor data from the one or more sensors in the elevator from when the passenger is detected entering the elevator from a first lobby to when the passenger is detected exiting the elevator at a second lobby; detecting the passenger exiting an elevator to a second lobby using 3D sensor data from one or more sensors positioned within the elevator; receiving floor position data associated with the floor position of the second lobby at a time proximate to when the passenger is detected exiting the elevator; generating a traffic list with arrival timestamps for each passenger transition from the first lobby to the second lobby where the traffic list comprises: the timestamp associated with the arrival of the passenger, the floor position data associated with the floor position of the first lobby at a time proximate to when the passenger is detected entering the elevator, and the floor position data associated with the floor position of the second lobby at a time proximate to when the passenger is detected exiting the elevator.
 29. The method as recited in claim 28, wherein, the time data to establish a timestamp associated with the arrival of the passenger is the time when the passenger is detected entering the elevator.
 30. The method as recited in claim 28, wherein the floor position data associated with the floor position of elevator.
 31. The method as recited in claim 28, wherein the floor position data associated with the floor position of the elevator is received from a sensor mounted in the elevator.
 32. The method as recited in claim 28, wherein tracking each individual passenger is maintained by detecting a head of each individual passenger via at least one of: a circle-Hough transform or particle filtering.
 33. The method as recited in claim 28, wherein the generated traffic lists for all elevators in the same group of elevators or in the same building are consolidated into a combined traffic list.
 34. The method as recited in claim 28, further comprising, identifying the specific door that the passenger entered in an elevator that has multiple doors and including the entrance door information in the generated information for the passenger transition.
 35. The method as recited in claim 28, further comprising, identifying the specific door that the passenger exited from an elevator that has multiple doors and including the exit door information in the generated information for the passenger transition.
 36. The method as recited in claim 28, wherein the generated information for the passenger transition from the first lobby to the second lobby also comprises identification of the elevator.
 37. The method as recited in claim 28, wherein the generated information for the passenger transition from the first lobby to the second lobby comprises an amount of time that the passenger spends inside the car between when the passenger is detected entering the elevator and when the passenger is detected existing the elevator.
 38. The method as recited in claim 28, further comprising, detecting the first arrival of an individual passenger in a first lobby, wherein the tracking is performed using 3D depth sensor data from one or more sensors mounted inside the first lobby; receiving time data associated with the detection of the arrival of the passenger into the first lobby; determining the passenger is boarding a particular elevator based on the position of the passenger relative to the known location of each elevator; tracking the passenger within the first lobby using 3D depth sensor data from the one or more sensors in the first lobby from when the passenger arrival is detected to when the passenger is detected boarding a particular elevator; associating the passenger detected boarding an elevator in the first lobby using the 3D sensor data from one or more sensors in the first lobby with the passenger detected entering the same elevator from the first lobby using 3D sensor data from one or more sensors positioned within the elevator; generating information for the passenger transition from the first lobby to the second lobby where the time data associated with the arrival of the passenger is the time data associated with the detection of the arrival of the passenger into the first lobby.
 39. The method as recited in claim 38, further comprising: associating of one or more passengers detected boarding the elevator in the first lobby using the 3D sensor data from one or more sensors in the first lobby with the passenger detected entering the same elevator from the first lobby using 3D sensor data from one or more sensors positioned within the elevator comprises at least one of: matching the order of passenger boarding an elevator as detected by the 3D sensor data from one or more sensors in the first lobby with the order of passengers entering the same elevator as detected by the 3D sensor data from one or more sensors positioned within the elevator. minimizing a measure of the time difference between the time when a passenger as detected by the 3D sensor data from one or more sensors in the first lobby with the order of passengers entering the same elevator as detected by the 3D sensor data from one or more sensors positioned within the elevator.
 40. The method as recited in claim 38, further comprising: associating of one or more passengers detected boarding the elevator in the first lobby using the 3D sensor data from one or more sensors in the first lobby with the passenger detected entering the same elevator from the first lobby using 3D sensor data from one or more sensors positioned within the elevator matches the order of passenger boarding an elevator as detected by the 3D sensor data from one or more sensors in the first lobby with the order of passengers entering the same elevator as detected by the 3D sensor data from one or more sensors positioned within the elevator.
 41. The method as recited in claim 38, further comprising: associating of one or more passengers detected boarding the elevator in the first lobby using the 3D sensor data from one or more sensors in the first lobby with the passenger detected entering the same elevator from the first lobby using 3D sensor data from one or more sensors positioned within the elevator minimizes a measure of the time difference between the time when a passenger as detected by the 3D sensor data from one or more sensors in the first lobby with the order of passengers entering the same elevator as detected by the 3D sensor data from one or more sensors positioned within the elevator.
 42. The method as recited in claim 38, further comprising: generating information for the passenger transition from the first lobby to the second lobby that comprises the time when the passenger is detected boarding an elevator.
 43. The method as recited in claim 38, further comprising: generating information for the passenger transition from the first lobby to the second lobby that comprises an amount of time the passenger waited in the first lobby between the time of passenger arrival into the first lobby was detected and the time when the passenger is detected boarding an elevator.
 44. The method as recited in claim 38, further comprising: detecting the position in the first lobby where the passenger was first detected arriving in the lobby; and generating information for the passenger transition from the first lobby to the second lobby that comprises the position in the first lobby where the passenger was first detected arriving in the lobby.
 45. The method as recited in claim 44, wherein generating information comprises generating a timestamped list of each passenger's transition from the first lobby and second lobby.
 46. A passenger tracking system for tracking a passenger transition from at least one of a first lobby to an elevator from the elevator to a second lobby, comprising: an elevator movable between a first lobby and a second lobby; a depth-sensing sensor within the elevator for capturing sensor data wherein the sensor data is 3D depth data; a processing module in communication with the depth-sensing sensor to receive the sensor data, where the processing module uses the sensor data to perform operations, comprising: receiving time data to establish a timestamp associated with the arrival of the passenger; receiving floor position data associated with the floor position of the first lobby at a time proximate to when the passenger is detected entering the elevator; tracking the passenger movement while within the elevator using 3D depth sensor data from the one or more sensors in the elevator from when the passenger is detected entering the elevator from a first lobby to when the passenger is detected exiting the elevator at a second lobby; detecting the passenger exiting an elevator to a second lobby using 3D sensor data from one or more sensors positioned within the elevator; receiving floor position data associated with the floor position of the second lobby at a time proximate to when the passenger is detected exiting the elevator; generating a traffic list with arrival timestamps for each passenger transition from the first lobby to the second lobby where the traffic list comprises: the timestamp associated with the arrival of the passenger, the floor position data associated with the floor position of the first lobby at a time proximate to when the passenger is detected entering the elevator, and the floor position data associated with the floor position of the second lobby at a time proximate to when the passenger is detected exiting the elevator.
 47. The system as recited in claim 46, wherein the processing module is operable to obtain the time data to establish a timestamp associated with the arrival of the passenger is the time when the passenger is detected entering the elevator.
 48. The system as recited in claim 47, wherein the time data comprises a first time interval that comprises an amount of time a passenger waits in the first lobby for the elevator to arrive, a second time interval that comprises an amount of time the elevator doors are open, and a third time interval that comprises an amount of time a passenger spends in the elevator.
 49. The system as recited in claim 46, wherein the processing module is operable to obtain floor position data associated with the floor position of the elevator from the elevator controller.
 50. The system as recited in claim 46, wherein the depth-sensing sensor comprises a structured light measurement, phase shift measurement, time of flight measurement, stereo triangulation device, sheet of light triangulation device, light field cameras, coded aperture cameras, computational imaging techniques, simultaneous localization and mapping (SLAM), imaging radar, imaging sonar, scanning LIDAR, flash LIDAR, Passive Infrared (PIR) sensor, and small Focal Plane Array (FPA), or a combination comprising at least one of the foregoing. 